|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 10.3.2
|
|
Title:
|
Amendment to MEF 10.3 - UNI Resiliency Enhancement, October 2015
The attributes of Ethernet Services observable at a User Network Interface (UNI) and from User Network Interface to User Network Interface (UNI to UNI) are defined. This document amends MEF 10.3 to enhance the UNI Resiliency Service Attribute to include multiple physical links that can carry different Service Frames simultaneously at a UNI.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2015
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet service attributes in MEF 10.3 form the basis of this Recommendation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known issues.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Amendment of MEF 10.3
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] IEEE Std 802.1AX – 2008, IEEE Standard for Local and metropolitan area networks – Link Aggregation, November 2008. /
[2] IEEE Std 802.1Q – 2011, IEEE Standards for Local and metropolitan area networks—Media Access Control (MAC) Bridges and Virtual Bridge Local Area Networks, 31 August 2011. /
[3] IEEE Std 802.3 – 2012, Standard for Ethernet, September 2012. /
[4] International Telecommunication Union, Recommendation G.781, Digital terminal equipments – Principal characteristics of multiplexing equipment for the synchronous digital hierarchy, 2008. /
[5] International Telecommunication Union, Recommendation G.8264, Packet over Transport aspects – Quality and availability targets, October 2008. /
[6] International Telecommunication Union, Recommendation Y.1563, Ethernet frame transfer and availability performance, 2009. /
/
[7] International Telecommunication Union, Recommendation Y.1564, Ethernet service activation test methodology, May 2011. /
[8] Internet Engineering Task Force RFC 2119. Key words for use in RFCs to Indicate Re-quirement Levels, March 1997. /
[9] Internet Engineering Task Force RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers, December 1998. /
[10] Internet Engineering Task Force RFC 2579. Textual Conventions for SMIv2, April 1999. /
[11] Internet Engineering Task Force RFC 3393, IP Packet Delay Variation Metric for IP Performance Metric (IPPM), November 2002. /
[12] Metro Ethernet Forum MEF 6.1, Ethernet Services Definitions - Phase 2, April 2008. /
[13] Metro Ethernet Forum, MEF 6.1.1, Layer 2 Control Protocol Handling Amendment to MEF 6.1, January 2012. /
[14] Metro Ethernet Forum MEF 7.2, Carrier Ethernet Information Model, April 2013. /
[15] Metro Ethernet Forum MEF 10.2, Ethernet Services Attributes Phase 2, October 2009. /
[16] Metro Ethernet Forum MEF 10.2.1, Performance Attributes Amendment to MEF 10.2, January 2011. /
[17] Metro Ethernet Forum MEF 12.1, Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services Layer - Base Elements, April 2010. /
[18] Metro Ethernet Forum MEF 16, Ethernet Local Management Interface (E-LMI), Janu-ary 2006. /
[19] Metro Ethernet Forum MEF 17, Service OAM Framework and Requirements – Phase 1, April 2007. /
[20] Metro Ethernet Forum MEF 20, User Network Interface (UNI) Type 2 Implementation Agreement, July 2008. /
[21] Metro Ethernet Forum MEF 22.1, Mobile Backhaul Phase 2, January 2012. /
[22] Metro Ethernet Forum MEF 23.1, Carrier Ethernet Class of Service Phase 2, January 2012. /
[23] Metro Ethernet Forum MEF 26.1, External Network Network Interface (ENNI) –Phase 2, January 2012. /
[24] Metro Ethernet Forum MEF 28, External Network Network Interface (ENNI) Support for UNI Tunnel Access and Virtual UNI, October 2010. /
/
[25] Metro Ethernet Forum MEF 30.1, Service OAM Fault Management Implementation Agreement: Phase 2, April 2013. /
[26] Metro Ethernet Forum MEF 33, Ethernet Access Services Definition, January 2012. /
[27] Metro Ethernet Forum MEF 31, Service OAM Fault Management Definition of Man-aged Objects, January 2011. /
[28] Metro Ethernet Forum MEF 35, Service OAM Performance Monitoring Implementa-tion Agreement, April 2012. /
[29] Metro Ethernet Forum MEF 36, Service OAM SNMP MIB for Performance Monitor-ing, January 2012. /
[30] Metro Ethernet Forum MEF 38, Service OAM Fault Management YANG Modules, April 2012. /
[31] Metro Ethernet Forum MEF 40, UNI and EVC Definition of Managed Objects, April 2013. /
|
|
9.
|
Qualification of
MEF:
|
|
|
The MEF was recognized under the provisions of ITU-T Recommendation A.5 on 24 September 2002. Qualifying information is on file with TSB.
9.5 The IPR policy of the MEF may be found in Article 10 of the MEF Bylaws which are available on the MEF public WEB site metroethernetforum.org.
9.6 All MEF Technical Specifications, Implementation Agreements, and Test Specifications are approved by an electronic letter ballot of all MEF members. For a MEF document to pass an electronic letter ballot at least a quorum of members (defined by the MEF bylaws as 1/3 of the MEF membership) must vote Yes or No. In addition, of the Yes plus No votes at least 75% of the votes must be Yes.
9.7 All published MEF documents are available for download free of charge in PDF or WORD format from the MEF public WEB site www.metroethernetforum.org .
9.8 Each revision of a given MEF document has a different MEF number.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
